Skip to content
This repository has been archived by the owner on Jan 27, 2023. It is now read-only.

Update base packages to use new paths #90

Merged
merged 1 commit into from
Jun 29, 2020

Conversation

ruflin
Copy link
Member

@ruflin ruflin commented Jun 29, 2020

As discussed in elastic/package-registry#565 the names of the directories should only use _ and no -. This updates the base package to use both directories in parallel.

As discussed in elastic/package-registry#565 the names of the directories should only use `_` and no `-`. This updates the base package to use both directories in parallel.
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: [Pull request #90 opened]

  • Start Time: 2020-06-29T07:07:59.664+0000

  • Duration: 7 min 12 sec

Test stats 🧪

Test Results
Failed 0
Passed 12
Skipped 0
Total 12

@ruflin ruflin requested a review from mtojek June 29, 2020 07:17
@ruflin ruflin merged commit 4d0ccfb into elastic:master Jun 29, 2020
@ruflin ruflin deleted the update-base-package-index-template branch June 29, 2020 08:03
thomasneirynck pushed a commit to thomasneirynck/package-storage that referenced this pull request Sep 28, 2021
)

There was a mix of using package, manifest or integration for the same thing in the code because of historical reasons. This PR introduces the Package struct with multiple methods and package is now used across the code. The methods on the Package struct also simplify the implementation of the search and categories endpoint.

Validation of the manifest.yml file for the version now happens when creating a package instance. This makes later checks for the version simpler and we detect issues earlier. The errors already show up on build time because of this.

Some of the docs comments were cleaned up or extended for better readability of the code.

Having a separate Package struct with methods also helps adding further unit tests without having to build packages.

No functionality was changed in this PR.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants